home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CD ROM Paradise Collection 4
/
CD ROM Paradise Collection 4 1995 Nov.iso
/
program
/
vseg10.zip
/
__001.EXE
/
MANUAL.DOC
< prev
next >
Wrap
Text File
|
1995-02-09
|
53KB
|
1,215 lines
Visible::Setup-G
--------------------
VGA splashcreen edition of Visible::Setup(tm),
developers' installation utility for DOS applications
a product of RCCO Research
Setup Summary
--------------
The following is a quick summary of steps that will be taken by the developer
to create an installation sequence with Visible::Setup-G:
┌────────────────────────────────────────────────────────────────────────┐
│ │
│ 1. Prepare a developer-designed VGA .pcx image (640x480x16) for │
│ the installation setup that will serve as a sign-on splashscreen. │
│ │
│ 2. You will create a self-extracting archive file named __001.EXE │
│ with LHA (included), PKSFX, or similar programs; __001.EXE will │
│ contain all your program's files that are to be installed on an │
│ end-user's machine. │
│ │
│ 3. Your program's documentation must be named MANUAL.DOC and must │
│ be included within the __001.EXE package. MANUAL.DOC should be │
│ plain ASCII text, suitable for printing to PRN from the DOS │
│ prompt. │
│ │
│ 4. If you wish your program and/or company names to be displayed │
│ on the opening screen banner (non-VGA systems) and elsewhere in │
│ your installation (all systems), create a one-line ASCII text file │
│ named _ADMIN.DAT that contains nothing other than that which you │
│ wish displayed (i.e., "MEGA-APP by XYZ SOFTWARE"). │
│ │
│ 5. Copy __001.EXE, your _ADMIN.PCX, the opt. _ADMIN.DAT, & INSTALL.EXE │
│ (the Visible::Setup-G program) to the root directory of your master │
│ distribution diskette, along with any other files (i.e., those not │
│ included inside __001.EXE) you wish to be included on each distrib- │
│ uted disk: README.TXT, FILE_ID.DIZ, VENDOR.DOC, etc. │
│ │
│ 6. Change to the drive containing your newly created master distribu- │
│ tion disk, and type INSTALL <enter> to test your firm's new │
│ installation routine. │
│ │
└────────────────────────────────────────────────────────────────────────┘
MANUAL.DOC Visible::Setup-G Documentation Page 2
Capabilities
-------------
Visible::Setup-G is a special edition of the Visible::Setup(tm) installation
utility that will display a developer-designed VGA .pcx file (640x480x16) as
a sign-on splashcreen for a customized introduction to the install program.
After the image display, Visible::Setup-G performs the same type of text-mode
installation procedure as the standard version of Visible::Setup. Non-VGA
systems will display the same opening screen (a text-mode splashscreen with
customizable banner) as with the standard version of Visible::Setup.
Visible::Setup-G is a simple, basic install utility for DOS applications.
It is easier for the developer to configure an installation sequence with
Visible::Setup-G than with batch files (i.e., the much-maligned
'install.bat'), yet far more elegant and professional in execution and
appearance. In utilizing Visible::Setup-G, there is no scripting language
to learn, there are no scripts or macros to write, nor are there unusual
setup practices that deviate from customary, familiar usage in the DOS
environment. Visible::Setup-G provides a clean, professional image to all
application installations.
While there are many available install programs for use by developers, all
of which claim easy configuration, in practice they sometimes have inherent
eccentricities that are inappropriate for use in many applications; often,
a garish overuse of color mix and screen images irrelevant to the task at
hand is prevalent (even in expensive commercial installation programs) and
is often simply not appropriate in professional development environments.
End-users, experienced or not, performing such resulting installations are
often confused and (rightly) concerned about current operations being carried
out on their machines. Each new instance of the configuration process for
the developer is often needlessly proprietary, time-consuming, and unwel-
comed.
Visible::Setup-G attempts to minimize such concerns, distractions, and eccen-
tric feature sets; it does this by offering the most simple solution possible
to the program installation process. The tradeoff for such simplicity is
that elaborate custom configurations on destination computers are not approp-
riate with this utility, other than those which may be carried out discretely
via a developer-created batch file option (see below).
Color usage and screen text formatting during the installation process itself
is clean, simple, and intentionally compatible with traditional DOS text, as
the program makes judicious use of DOS services (inherent in command.com)
during the installation process. Colors, attributes, and screen prompts are
specifically designed to be usable and visible on all color, monochrome, and
laptop/notebook displays.
Visible::Setup-G is used in conjunction with any of the widely available
archiving/compression programs that produce a self-extracting compressed
file. The examples in this documentation use the LHA file-compression
program by Haruyasu Yoshizaki, considered by many developers as an accepted
standard for professional use (i.e., several of the large commercial software
publishers use LHA, particularly for demo installations, because of its
speed, reliability, and ease of setup). A copy of LHA.EXE is provided for
evaluation within the current package. Other compression programs that
MANUAL.DOC Visible::Setup-G Documentation Page 3
produce self-extracting archive files may be used as well within
Visible::Setup-G, as long as the resulting compressed filename extension
is .exe.
The unregistered evaluation version of Visible::Setup-G, provided herewith,
is fully functional. Its limitation provides for installations that will
fit on a single install diskette (360k, 720k, 1.2mg, 1.44mg - as needed).
The registered copy version provides for installations that span multiple
disks in any single installation set. Visible::Setup-G provides advantages
for the commercial developer in that, upon payment of a very nominal
registration fee (currently $44.95), it may included and distributed with
multiple applications legally and without further license, restriction, or
payment of runtime royalties.
The demonstration for the Visible::Setup-G program is provided by performing
an installation of itself. The potential developer user of this product
may begin evaluation of Visible::Setup-G by observing its installation:
the developer's resulting installations will have similar execution and
appearance.
Visible::Setup-G may be used with most traditional MS-DOS language ins-
tallations, including those created with CA-Clipper, Borland Turbo Pascal,
QuickBASIC, PowerBasic, Visual Basic(tm) for DOS, dBase, Clarion, FoxPro, C,
etc. It is small, efficient, and executes cleanly and swiftly from DOS (or
a full-screen DOS box in Windows(tm)). Its small file size (about 24k, not
compressed) provides for minimal space usage on distribution disks.
Visible::Setup-G may well be particularly appropriate for corporate
developers transmitting applications to remote locations.
Visible::Setup-G installations will run under both DOS and Windows(tm).
The chief advantages, aside from those described above, are both low cost
and method of acquiring. The copy included herewith is a fully-functional
evaluation copy available easily and universally through the user-supported
software marketplace.
[ Please note the similarly-named edition of Visible::Setup-G called
Visible::Setup -- the standard version of the program. The standard version
of Visible::Setup, also from RCCO Research, works solely in text-mode and
offers a similar type of installation procedure; we point out the similar
names to help avoid confusion about the two products. ]
MANUAL.DOC Visible::Setup-G Documentation Page 4
Self-installation is the demonstration
---------------------------------------
To observe the demonstration of how Visible::Setup-G works and appears,
simply install Visible::Setup-G to your hard disk by logging on to the drive
containing the installation files, then typing:
INSTALL <enter>
If the program has been downloaded from a BBS or information service, you
may run INSTALL.EXE from your downloads directory if you are installing to
a *different* logical drive from the one in which INSTALL.EXE exists. (You
may wish to include this paragraph or something similar regarding downloads
in your README.TXT file for your own installations.)
The install process will create a directory on the destination drive if it
does not already exist, the default selection being \PROGRAMS (please feel
free to specify a different directory name). The install process does not
modify the path, autoexec.bat, or config.sys.
Before the end of the installation, an optional developer-defined batch file
named '_setup.bat' is called discretely and unobtrusively. In the installa-
tion of Visible::Setup-G itself, _setup.bat occurs as a simple page of text
to show when and where it might appear in the install process, should the
developer wish to make use of such a batch file for special configurations,
operations, or welcome messages, etc. _Setup.bat is deleted from the
directory after execution, so that the end-user is not ordinarily aware of
its existence or use. In other installation instances, should a _setup.bat
file be found not to exist, the installation simply ends appropriately at
this point.
Splashscreens and banners
--------------------------
For VGA systems:
If the user is logged onto the source drive when launching INSTALL.EXE,
a developer-designed VGA .pcx file (640x480x16) is displayed as a sign-on
splashcreen for a customized introduction to the installation sequence.
If the user is *not* logged onto the source drive when launching INSTALL
(i.e., the user typed A:INSTALL from the C: drive or elsewhere other than
the source drive), the program will exit with a message for the end-user to
begin the installation by logging onto the source drive. Specifically, that
message reads:
Installation file _admin.pcx not found in current directory.
Make the drive containing the installation files the CURRENT drive.
i.e., type "A:" or "B:" and press <enter>.
Then type "Install" <enter>.
MANUAL.DOC Visible::Setup-G Documentation Page 5
After installation commences, should an optional file '_admin.dat' be found
to exist, the program name and developer's company name are displayed on the
following screen which requests info as to the source drive, and again on the
very final screen.
For non-VGA systems:
If the user is logged onto the source drive when launching INSTALL.EXE,
the developer's program name and company name are read from an optional file
named '_admin.dat' and are displayed on the opening screen as a banner, and
on the second screen which requests info as to the source drive, and again
on the very final screen.
If the non-VGA user is not logged onto the source drive when launching INSTALL
(that is, the user typed A:INSTALL from the C: drive or elsewhere other than
the source drive), the installation process will commence (note the difference
in events from that of a VGA system here) with no banner on the standard
text-mode splashscreen, and the names are displayed only on the final screen
as part of the epilogue. In this instance, an _admin.dat file must be
present on the source drive for the names to be displayed at the end.
For all video systems:
Please note that the use of _admin.dat is entirely optional.
Preparation of pcx images for the splashscreen
-----------------------------------------------
The VGA image display is particularly effective for software developers
preparing a customized welcome, copyright, or other splashscreen to introduce
the installation of their product. They may easily capture usable materials
with programs like Hijaak(tm) for Windows and modify or create them in
editing programs such as Windows(tm) Paintbrush.
The only requirement is that images must be finally saved in 640x480 16-
color VGA .pcx file format. If you are doing image preparation in Windows,
you will have to load a 16-color video driver for 640x480 VGA in order to
prepare proper images. This format is used since it is the most universal
that will allow presentations to be viewed on as many DOS and/or Windows
VGA systems as possible. Do not build your images with 256 or more colors
as they may not display properly with Visible::Setup-G. The end-user should
then be able to display the image using any VGA card and driver with 16 or
more colors; it is only during the preparation and saving of .pcx images that
you must use a 640x480x16 driver.
We have observed excellent, consistent results with using a program such as
Hijaak(tm) for Windows to capture entire DOS or Windows screens, or selected
areas of screens, or a particular window on a full Windows screen. The
preparer then does final editing, adding text, drawing lines or other objects,
in a drawing program. For example, the sample sign-on screen provided with
this package was done entirely in the program that comes free with Windows:
Paintbrush. The inset picture was captured from a black and white line
drawing with a hand scanner and edited in Paintbrush.
MANUAL.DOC Visible::Setup-G Documentation Page 6
Other graphics programs are likely to provide compatible material, but they
must be tried on a test basis with Visible::Setup-G. The two programs
mentioned above work well for most users, are widely available, and do not
require great technical or professional ability. Scanned images will be
effective in Visible::Setup-G if they are saved in the proper format. If
one format you are using seems not workable, try saving that image in another
program, such as Windows Paintbrush; we have often found that certain images
work better when converted or simply saved in another program's format even
though they may use the same .pcx extension.
When attempting to use monochrome pcx files, resave them as 16-color
640x480 VGA pcx files. Even though the appearance may remain the same,
they will be saved in a format usable by Visible::Setup-G.
The splashscreen image displayed at the outset of an installation sequence
will stay in view until the user presses a key. We suggest that you include
somewhere on your image (perhaps at lower-right) the words
"Press a key..."
to indicate to your end-users that the installation program is waiting for an
action on their part.
Once you find the right combination of steps to produce pcx file formats
consistently usable by Visible::Setup-G, you will save a great deal of time
and effort by always using that combination in future installation
applications.
Required naming convention for the .pcx file
---------------------------------------------
After you have prepared the desired .pcx file, simply rename it
_ADMIN.PCX
The basic requirement is that the image file and the related INSTALL.EXE be
found in the same directory on an installation drive. (Due to the slowness
of building the on-screen image when reading from a floppy diskette, it may
be worthwhile to advise end-users that installation from a ram drive or
hard-disk directory will yield superior results.)
Your end-users will certainly need VGA graphics capabilities to view your
splashscreen. If a user attempts execution on a non-VGA-capable system,
a text-mode splashscreen (with optional customizable banner) will introduce
the installation sequence.
MANUAL.DOC Visible::Setup-G Documentation Page 7
Preparation of files to be installed
-------------------------------------
There are two required appropriately-named files that must exist for use
with Visible::Setup-G. There must be a self-extracting compressed archive
file named
__001.EXE
containing all the files the developer wishes installed on end-users'
machines.
We utilize the unusual naming convention (__001.EXE) for archive files in
order to discourage inadvertant launching of the extraction process by an
end-user at an inappropriate time (i.e., on a floppy diskette with
insufficient space for decompressed files). We have found this naming
practice to work quite well in many of our own commercial applications of
recent years.
The Visible::Setup-G disk identification procedure tests for the presence of
a file named __001.EXE; without the presence of such a file, the end-user will
be prompted for insertion of the installation disk in the specified source
drive.
Inside the __001.EXE must exist the other required file:
MANUAL.DOC
The MANUAL.DOC ordinarily contains your program information and instructional
material for end-users. Each instance of an install with the Visible::Setup-G
program will check for the existence of a file called MANUAL.DOC in the des-
tination directory as part of the verification of successful completion of
installation. The installation also prompts the end-users as to whether or
not they wish to print out a copy of the program documentation on their
printers. In order for them to do that, the file must exist and it must be
named MANUAL.DOC. If it is absent, an error message will be displayed that
informs them a file is missing; the installation process will exit at that
point with a message indicating an incomplete installation.
MANUAL.DOC need not be elaborate or very long (even a single page will do),
but it must be a plain ASCII text file suitable for printing to PRN from the
DOS prompt (more about this further on).
Please note that MANUAL.DOC must be placed *inside* the __001.EXE package.
MANUAL.DOC Visible::Setup-G Documentation Page 8
The _Setup.bat option
----------------------
In addition to the developer's program files and the MANUAL.DOC, __001.EXE
may contain a developer-defined batch file, named
_SETUP.BAT
as mentioned previously.
The use of a _setup.bat is optional, but is provided to afford the developer
the opportunity for custom configurations or simply a personal welcome or
thank you message for the end-user. A _setup.bat may be used if the devel-
oper needs to create subdirectories (and move files into such subdirector-
ies), check config.sys settings or display critical messages (i.e., 'Make
certain the FILES= setting in your config.sys file is set to FILES=30 or
greater') or provide initial operating instructions (i.e., 'With the included
copy of LIST.COM, you may read the documentation by typing LIST MANUAL.DOC
and pressing Enter'), etc.
The _setup.bat need not display any message at all while it is performing
custom configuration commands, but it may do so if the developer so wishes.
It will execute as if normally executed from the DOS prompt in the directory
where the developer's program has just been installed.
The developer should exercise caution against attempting to launch large
executable programs from within the _setup.bat sequence. There can be no
assurance that sufficient memory will be available for the child process on
all potential users' machines. _Setup.bat is intended primarily for calling
on DOS functions found in command.com, i.e., MD, COPY, DEL, etc. Always
return your end-users to the main program directory after performing your
custom actions. You should well test all events and all possible
consequences of those events before distributing your programs.
_Setup.bat is deleted from the destination directory after its execution, so
that the end-user would not ordinarily become aware of its existence or use
by finding it in the program directory. If, during any instance of an ins-
tallation, a _setup.bat file is not found to exist, the installation ends
appropriately and normally at that point. In either situation, with or with-
out the _setup.bat sequence, Visible::Setup-G then completes its function,
with an on-screen indication to the end-user of a successful installation.
Please note that _setup.bat must be placed *inside* the __001.EXE package.
MANUAL.DOC Visible::Setup-G Documentation Page 9
The _Admin.dat file option
---------------------------
As mentioned previously, if a properly constructed file named '_admin.dat'
is found on the source drive, Visible::Setup-G can display the developer's
program name and/or company name at least once and normally three times
during the non-VGA installation and twice during a VGA sequence.
_Admin.dat must be a plain ASCII text file consisting of one line only, with
no more than 76 characters in the one line; it must be left-justified within
_admin.dat. It should appear similarly as follows:
MEGA-APP by XYZ SOFTWARE
although the content and format may of course be determined by the developer
within the limitations described above.
You create an _admin.dat with your text editor or simply modify the sample
one included with this package. You then include a copy of _admin.dat in
the root directory of your master installation disk 1.
During an installation, if the end-user is logged onto the source drive when
launching INSTALL.EXE, i.e.,
A: <enter>
INSTALL <enter>
the developer's VGA splashscreen is displayed on VGA systems; on non-VGA
systems, the developer's program name and/or company name is read from the
_admin.dat and is displayed on the opening screen as a banner. (Expressed in
another way, the location of _admin.dat must be in the current directory of
the currently logged drive in order to be read into the install procedure for
the non-VGA splashscreen.)
If the user is *not* logged onto the source drive when launching install on
a non-VGA system, i.e., the user typed:
A:INSTALL <enter>
(or
B:INSTALL <enter>)
from the C: drive or elsewhere other than the source drive, the name(s) are
displayed only on the final screen as part of the epilogue. In this ins-
tance, a proper _admin.dat file must be present on the source drive for the
name(s) to be read by Visible::Setup-G and displayed as described.
Similarly, if a VGA user is not logged onto the source drive when launching
INSTALL (i.e., the user typed A:INSTALL from the C: drive or elsewhere other
than the source drive), the program will exit with a message for the end-user
to begin the installation by first logging onto the source drive. This
action is to ensure that the developer's VGA splashscreen is displayed to
the end-user.
MANUAL.DOC Visible::Setup-G Documentation Page 10
We emphasize that _admin.dat must be plain ASCII text with no extraneous
formatting codes, and consist of one line only. We find that shorter line
lengths, when appropriate, offer more suitable banner appearance than longer
lines, even though technically you may have a line of up to 76 characters in
length.
If you do not care to have the name(s) displayed at all, simply omit an
_admin.dat file from your distribution disk 1.
Please note that _admin.dat is *not* placed inside the __001.EXE package,
but rather in the root directory of your distribution disk 1.
Use of the LHA.EXE compression utility
---------------------------------------
Within the Visible::Setup-G package should be found a copy of LHA.EXE, the
freeware file compression program by Haruyasu Yoshizaki (Yoshi), for your
evaluation. This quality utility offers an excellent compression ratio and
ease of use, along with a swift self-extracting mechanism appropriate for
use in installation sequences.
The creation of the required __001.EXE (see above) with LHA is a two-step
process. First, the compression package is created by indicating the files
desired within the archive; for example, one might enter at the DOS prompt:
lha a __001 myapp.exe *.dbf MANUAL.DOC readme.txt order.frm _setup.bat
followed by pressing the <enter> key. This creates an archive file named
__001.LZH containing the files indicated after the '__001' parameter. The
first parameter after the 'lha' command is the letter 'a' which simply
means ADD to an archive file named '__001' the filenames (separated by a
space in each instance) that follow. Conventional DOS wildcard characters
may be used, as indicated in the sample above.
The one *required* file in the archive is capitalized above for emphasis:
MANUAL.DOC
in that it must be present in any Visible::Setup-G installation. MANUAL.DOC
need not be elaborate (see below for suggestions for MANUAL.DOC), but it
must be present in all install setups that you create.
If you have a README.TXT that will appear on your distribution diskette,
and you would like it to be found in the end-users' program directory as
well, include a copy of it in the archive file, as indicated in the sample
above.
If you subsequently need to add other names to this archive at a later
time, the 'a' parameter is used again; i.e.,
lha a __001 *.ndx <enter>
adds all files ending in '.ndx' to the existing archive named __001(.LZH).
MANUAL.DOC Visible::Setup-G Documentation Page 11
Similarly, to delete a file from the archive, you specify:
lha d __001 _setup.bat <enter>
and the file named '_setup.bat' is removed from the archive package.
The __001.EXE file
-------------------
From the resulting archive file called __001.LZH you must then create a
self-extracting archive file by typing:
lha s __001 <enter>
This will create a self-extracting form of the archive named __001.EXE, which
will then be placed in the root directory of your master distribution disk 1
for use by Visible::Setup-G. You should NOT include a copy of LHA.EXE with
your distribution disk(s), since the self-extracting file executes and
decompresses your sequence of files on any DOS-compatible computer.
Please simply note the required filename for the compressed file package:
__001.EXE is made up of two underscore characters, followed by two zeros
(*not* the letter 'O'), followed by the digit 1.
(If the above LHA.EXE instructions are familiar and obvious to you, they
may seem simplistic in our iteration of them in this document; please be
mindful that they are *not* obvious to some users who may never have used
the LHA utility before.)
Maximum size for __001.EXE
---------------------------
Take care not to allow the __001.EXE file to exceed the capacity of your
intended distribution disk, minus about 24k for the Visible::Setup-G
executable file (install.exe) plus space required for the other needed files:
_admin.pcx, _admin.dat, readme.txt, file_id.diz, etc. If the __001.EXE
grows larger than available diskette space, either choose the next largest
disk size for your master distribution diskette or utilize an authorized
registered copy of Visible::Setup-G, which may span multiple disks (up to
six) when needed (with __002.EXE, __003.EXE, etc).
MANUAL.DOC Visible::Setup-G Documentation Page 12
MANUAL.DOC suggestions
-----------------------
As mentioned previously, the required file named MANUAL.DOC need not be
elaborate or lengthy, although it may of course be both. This is entirely
up to the developer and the requirements of each particular application.
In a Visible::Setup-G installation, MANUAL.DOC may be as short as one
page in length, but it must indeed exist.
MANUAL.DOC should be plain ASCII text created with a text editor or with a
word processor capable of saving files as plain ASCII text. Line length
should never exceed 79 characters and the text itself must never carry any
invisible formatting codes other than the formfeed character (Alt-12). Be
particularly cautious not to include the arrow characters (Alt-24, 25, 26,
27) in diagrams or other parts of the documents, as you could easily abort
the document printing process for the end-user during installation or at
other times. Be mindful that certain line-drawing or box characters may
not print appropriately on non-graphics printers; we include them in our
own documents, but use them judiciously with the assumption that our intended
audience has the appropriate hardware capability.
MANUAL.DOC should be generically formatted for proper appearance when printed
to PRN from the DOS prompt. Such basic format should include pagination and
proper formfeeds. An easy way to prepare this is to use two commonly
available utilities: PC Magazine's PRN2FILE.COM and Peter Norton's "Line
Print" program, LP.EXE. You load PRN2FILE, a TSR, to direct all print com-
mands ordinarily sent to LPT1 to a specified disk file (perhaps, for example,
to TEMP.TXT). You then issue an instruction to LP.EXE to "print" a copy of
your unformatted MANUAL.DOC with a 0 left margin. After PRN2FILE writes
this print run to a disk file, you will have a newly formatted copy of your
MANUAL.DOC suitable for printing to PRN from the DOS prompt. You may need
to edit the resulting copy slightly or experiment with moving paragraphs
down or up in your original copy in order to get an acceptable final copy,
but these operations take only minutes and are well worth the end result.
You may wish to make note in your README.TXT file (which may be included in
the root directory of your master distribution disk 1), that end-users will
be given an opportunity to print out the program documentation during the
installation process. You should also inform them of the number of pages in
the documentation, so that they may ready their printers with an adequate
supply of paper. We have found, over and over during recent years, that
many users very much appreciate the opportunity to print out program documen-
tation, from either the installation or within the application itself. You
might be mindful of your potential clientele and the fact that there are
many computer users that are uncomfortable with, or perhaps unknowledgeable
of (even with specific instructions), issuing a simple DOS command such as
"TYPE MANUAL.DOC > LPT1."
MANUAL.DOC Visible::Setup-G Documentation Page 13
The master distribution disk(s)
--------------------------------
After the required files are readied, you need only to copy them to the
root directory of your master distribution disk(s). The files will include:
INSTALL.EXE (the Visible::Setup-G executable file)
__001.EXE (self-extracting compressed file)
_ADMIN.PCX (developer-designed sign-on image)
_ADMIN.DAT (optional program/company names file)
as well as other files you might wish to be distributed, for example:
README.TXT
FILE_ID.DIZ
VENDOR.DOC (or INFO.TXT)
ORDER.FRM (perhaps should be inside __001.EXE)
etc.
If using an authorized copy of the registered version of Visible::Setup-G,
you will have multiple-disk set capacities. Disk 2 would contain __002.EXE,
Disk 3 __003.EXE, etc. Simply plan and adjust your __00?.EXE files to fit
properly on the intended size of distribution diskettes. The registered
version also makes provision for the developer to specify a different name
for the suggested default destination directory for each application, rather
than only the '\PROGRAMS' default suggested in the present version.
If you find that disk space on distribution disk 1 is not enough, the
INSTALL.EXE can usually be compressed with the LZEXE.EXE utility by Fabrice
Bellard. We caution that other .exe compression programs may not work well
in this instance.
Please note that all required files should be placed in the root directory
of your distribution disk(s).
MANUAL.DOC Visible::Setup-G Documentation Page 14
The sequence of events during an installation
----------------------------------------------
When the user has launched INSTALL.EXE from the DOS prompt (or a DOS box in
Windows) on a non-VGA system, a splashcreen is displayed prompting the user
to press <Enter> to initiate the installation process. VGA users will be
presented with the developer's pcx sign-on image which will stay in view
until the user presses a key.
The following screen prompts for the letter of the source drive containing
the installation Disk 1, with the default suggesting Drive A:. The user
may press any letter corresponding to the available DOS drives on the
computer, or may simply press <Enter> to accept the default. INSTALL will
use the currently logged directory on the source drive, which is normally
the root on a floppy drive or, if installing from a hard drive (or a ram
drive), the current directory from which INSTALL was launched. If the user
presses <Esc> at this point, the install program will exit and return to
the system.
After the source drive prompt, a screen prompting for the destination drive
is displayed. It will be indicated to the user that the source drive and
destination drive must be different. Again, the user presses a letter key
corresponding to an available drive letter, or presses <Enter> to accept the
default, which is hard drive C:. <Esc> at this point will exit the install
process.
The next screen prompts for a destination directory on the previously chosen
destination drive. The suggested default is \PROGRAMS (the registered ver-
sion provides for the developer to change the directory name to another sug-
gested default), but the user is free to enter any directory name, either
existing or needing to be created, allowable under DOS naming conventions.
If the user enters an inappropriate name, an error message will be displayed
with a suggestion for proper naming procedures allowed under DOS. For exam-
ple, a common error might be to enter a second subdirectory,
\DIR1\DIR2
when \DIR1 does not prior exist. For such users, the error message suggests
they enter a DOS-allowable directory name or simply accept the default direc-
tory name suggested by INSTALL.
The next screen displays information that the installation has begun and
offers other informative messages as the process proceeds. The occurrence
here is one of copying the __00?.EXE files from the source drive to the
destination directory, unarchiving the compressed files, and removing the
__00?.EXE files from the program directory. Part of the verification
process includes checking for the presence of the file MANUAL.DOC at this
point; if this key file is missing, the user is informed of an incomplete
installation, and returned to the system with suggestions as to possible
solutions to the problem that occurred. The developer must ascertain that
omitting a MANUAL.DOC from the package will never be a cause for the end-
user seeing this message.
After the verification, the user is presented with a new screen prompting
that the documentation may be printed out and would they indicate by a
MANUAL.DOC Visible::Setup-G Documentation Page 15
<Y> or <N> response whether or not they wish to print the documentation.
If the user answers <N>, the install process continues to the next event.
If the user presses <Y>, a second prompt will ask the user to verify that
the printer is on, top of page aligned, and that there is sufficient paper
in the printer. Again, the response must either be <Y> or <N>. If <N>,
INSTALL discontinues the print request and proceeds to the next event.
If the user again responds <Y>, the file MANUAL.DOC is typed to the output
device PRN, along with an appropriate screen message to the user that the
printing process is underway.
Next, INSTALL checks the program directory for the existence of a _setup.bat
file, which would have been placed in that directory from within the
__001.EXE package. If _setup.bat is not found, INSTALL procedes to the next
event (the final screen). If it is found, it is immediately executed as a
process that appears to the end-user as part of the ongoing installation
sequence. Often the _setup.bat need only carry a welcome or thank you
message from the developer to the end-user. The developer should well
consider the significance and advantages that such well-placed messages
may convey to the client. Note: a clearscreen precedes the _setup.bat call.
The final screen indicates to the end-user successful completion of the
installation procedure and a return to the system prompt, in the program
directory.
Precautions
------------
One caveat we might offer with Visible::Setup-G is to make sure that the
optional _SETUP.BAT (the extension is .Bat for batch) file is placed
*inside* the __001.EXE package, while the optional _ADMIN.DAT (the extension
is .Dat for data) file is placed in the root directory of your distribution
disk 1. Keep in mind also that the file named MANUAL.DOC is used as a
key file for verification purposes; do not neglect to always include such
a file inside one of your __00?.EXE packages.
If you find that your pcx images do not display, or do not display properly,
it is probably because they have been created or saved in a format that may
only be slightly incompatible with that which Visible::Setup-G requires.
Before you decide that the Visible::Setup-G program is not usable in such
instances, try the suggestion given before for re-saving your .pcx files in
another graphics program. Most image-editing programs will read files in
several formats, and often allow conversions, or perhaps will save them in
a later .pcx format that will work with applications such as Visible::Setup-G.
Also, make certain that images are saved in 640x480 by 16-color format by
using the proper software and/or video drivers to handle the format.
MANUAL.DOC Visible::Setup-G Documentation Page 16
Program Requirements
---------------------
The requirements for creating Visible::Setup-G installation sequences
include a DOS-compatible PC with 512k memory. DOS 3.1 (or later) or Windows
3.x (or greater) should be utilized. To display a developer-designed VGA
.pcx splashscreen, the end-user must have a VGA-capable system; non-VGA
systems will display a default text-mode splashscreen with customizable
banner.
The Unregistered Evaluation Copy
---------------------------------
The unregistered version of this program is intended for use in evaluation
situations. It may be used for ninety (90) days within your own organ-
ization by persons that have knowledge and understanding of the fact that
it is an unregistered evaluation copy.
The payment of the $44.95 purchase price for a registered copy of this
program will allow license for a single user to make use of the program for
purposes that are traditionally accepted for software utilities of this
type. Additional site license fees of $20.00 per user may be paid at the
time of registration, or any time in the future after initial registration
at the then current license fee in effect. There are no runtime royalties
involved in the distribution of your materials utilizing a duly registered
copy of Visible::Setup-G.
The license and authorized registration shall not be construed as being
in effect until direct payment has been received by RCCO Research and an
authorized, registered copy has been sent in the registered user's/users'
name(s).
The Registered Version of Visible::Setup-G
-------------------------------------------
The registered copy performs functionally similar to the evaluation copy, and
includes specific copies of INSTALL.EXE that provide for multiple-disk set
installations, up to and including six- (6-) disk installations. The maximum
size of each __00?.EXE must be limited to that which will fit on the intended
size of the distribution disks (i.e., for 360k disks each __00?.EXE must not
exceed 360k or the next largest disk size should be utilized throughout the
set).
If you require a version of Visible::Setup-G that provides for a multiple-disk
setup greater than six disks, we can provide a custom build of INSTALL.EXE
for a very nominal fee. We can also make a custom build that omits the docu-
mentation printing sequence, for those developers that have pre-printed
materials. (Please write for a quotation, indicating the specific number of
install disks required in your application plus any other specifications.)
Such custom builds may be obtained with, or after, the initial registration
of the program.
MANUAL.DOC Visible::Setup-G Documentation Page 17
The registered version also makes provision for the developer to specify a
different name for the suggested default destination directory for each
application, rather than only '\PROGRAMS' as suggested in the evaluation
copy. With that provision, each new application that goes out may have
a developer-defined suggestion for the destination program directory.
Documentation for the registered version is an on-disk text file, similar to
the present format.
Your registered version disk (either 360k 5.25" or 720k 3.5", please specify)
will contain authorized, serialized copies of the latest version of the
Visible::Setup-G program along with license to distribute with your own
applications without undue restriction or payment of runtime royalites.
Any upgrade versions will be offered to registered users at significant
reduction from the then current registration fees.
Licensing Information
----------------------
This program is licensed and supplied as is, without any warranty. To the
extent permitted under applicable law, RCCO Research Associates disclaims
all warranties, either expressed or implied, with respect to this software
program, its quality, performance, merchantability, or fitness for any
particular purpose.
In particular, this software program is not guaranteed to prevent or detect
damage to your data or programs. In no event shall RCCO Research Associates
be liable for any claims for lost profits or any damage, including, but not
limited to, special, incidental, consequential or other damage (including,
without limitation, damages for loss of business profits, business interrup-
tion, loss of business information, or other pecuniary loss) arising out of
the use of or inability to use this RCCO Research Associates product, even
if RCCO Research Associates has been advised of the possibility of such
damages. Some states do not allow the exclusion or limitation of incidental
or consequential damages, so the above limitation or exclusion may not apply
to you. In no case shall RCCO Research Associates's liability exceed the
license fees paid for the right to use the licensed version of the software.
The license agreement and warranty shall be construed, interpreted and
governed by the laws of the state of Tennessee.
This software program is protected under the Copyright Laws of the United
States of America and all applicable International Copyright Conventions.
Makers and/or users of illegal or unauthorized copies of the registered
version are subject to prosecution under these laws.
The name Visible::Setup(tm) is a trademark of RCCO Research Associates.
Windows(tm) is a trademark of Microsoft Corporation. Other trade names
referenced herein are either trademarks or registered trademarks of their
respective companies.
MANUAL.DOC Visible::Setup-G Documentation Page 18
Registration Notes
-------------------
Registration will obtain a copy of the most recent authorized version and
provide legal authorization for continued use of the program after the
ninety-day (90-day) evaluation period.
To obtain a registered copy, you may mail an advance-payment registration
fee of U.S. $44.95 + $2.55 shipping/handling ($7.05 non-U.S. shipping/
handling, $4.05 for Canada) directly to RCCO Research. Additional users
are $20.00 per user. Payment is to be made by check or money order only,
please. We require payment with order so that prices and fees may be kept
as reasonable as possible; this policy has worked well for us in recent
years, as we observe increased registration on products that are reasonably
priced. For credit card and telephone orders, see the Additional Ordering
Options note below.
Currently registered users of the standard version of Visible::Setup may
purchase Visible::Setup-G at a special price; please contact RCCO Research
directly for specifics.
Visible::Setup-G has a different pricing structure for registration and fees
than does the standard version of Visible::Setup.
An invoice will be included with your order, showing the registered serial
number(s) applicable to the purchase. We can provide a pro forma invoice
to those corporations or institutions that require same before payment can
be issued; shipment will be made promptly upon receipt of payment. Prices
and/or registration and/or license fees are subject to change.
Tennessee clients please include the required 8.5% sales tax on both the
product amount and shipping/handling as mandated by the state.
International clients must pay by check or money order in U.S. dollars, drawn
on a U.S. bank or the U.S. branch of an international bank. Please realize
that international postal money orders are considerably delayed through the
postal systems and may not be the most expedient way of relaying payment. An
often-used form of payment consists of obtaining a dollar-denominated money
order from the local American Express office which you may then airmail to
us along with your order. International orders are dispatched promptly
when using a credit card order as outlined below, under Additional Ordering
Options.
Please indicate program name and current version number on your order; you
may use the Order.frm file provided on the disk (or the program directory)
or simply send a note or letter with your name, organization name, address,
program name & version, number of users being licensed, and remittance.
Your comments on our programs are welcomed.
MANUAL.DOC Visible::Setup-G Documentation Page 19
Additional Ordering Options:
----------------------------------------------------------------------
CREDIT CARD ORDERS ONLY -
You may order a registered copy of this RCCO Research program
with MasterCard, Visa, Amex, or Discover from PsL, Public (software)
Library of Houston, Texas by calling 800-242-4775 or 713-524-6394,
or by FAX to 713-524-6398, or by CompuServe E-mail to 71355,470.
You may also mail credit card orders to PsL at P.O. Box 35705,
Houston, TX 77235-5705. PsL's item/product number for
Visible::Setup-G is #11706.
THE ABOVE NUMBERS ARE FOR ORDERS ONLY.
Any questions about the status of the shipment of the order,
registration options, product details, technical support, volume
discounts, dealer pricing, site licenses, etc. must be directed in
writing to RCCO Research, P.O. Box 196, Gatlinburg, TN 37738. To
ensure that you get the fastest possible delivery of your registered
copy, PsL will notify us the day of your order and we will promptly
ship the materials directly to you. There are no additional fees
for ordering by credit card.
Your credit card number is *not* transmitted to RCCO Research, but
rather is processed by PsL as part of their software registration
service.
The above service is made available as a convenience to client
individuals who feel comfortable with ordering by telephone and
with a credit card. Established concerns may prefer to order
directly from RCCO Research with the company's own business check.
The PsL staff cannot answer non-order inquiries.
----------------------------------------------------------------------
Additional Information
-----------------------
If you have any comments or questions regarding this program after (or with)
registration, please send them to:
RCCO Research Associates
P. O. Box 196
Gatlinburg, TN 37738-0196 (U.S.A.)
Please include your phone (day & evening) and fax (if any) numbers as well
as your mailing address and CompuServe number / Internet address (if any) on
ALL written communications. Please indicate the serial number from your copy
of the program as well as your CustID number. Our E-mail addresses are
provided to registered users along with the invoice.
MANUAL.DOC Visible::Setup-G Documentation Page 20
RCCO Research is also the publisher of several other development tools,
including:
Visible::Serialization(tm), developers' serialization utilities. Append
a serial number (or other identifier) to an .exe; create and/or increment
such serial numbers; search for and display serial numbers.
Visible::Serialization may be used with most traditional MS-DOS or Windows
executables, including those created with CA-Clipper, Borland Turbo Pascal,
QuickBASIC, PowerBasic, Visual Basic(tm) for Windows or DOS, FoxPro, Clarion,
C, Visual C++, etc.
Please consult your favorite user-supported software source for the
availability of Visible::Serialization and other RCCO Research development
tools.
Visible::Setup-G
-----------------
VGA splashcreen edition of Visible::Setup(tm),
developers' installation utility for DOS applications
(C) Copyright 1994-95 RCCO Research Associates
All Rights Reserved under International Conventions
Product of U.S.A.
RCCO Research Associates
Post Office Box 196
Gatlinburg, Tennessee 37738 (U.S.A.)
┌─────────────────────────────────┐
│ RCCO Research Associates │
│ Technical Publishers, Est. 1965 │
└─────────────────────────────────┘